Baseboard management controller and method of loading firmware

ABSTRACT

Disclosed is a baseboard management controller (BMC) that may include a bootloader, and an interface to a removable storage device having a first firmware file. The bootloader may be configured to load the first firmware file from the removable storage device for the BMC to run a kernel.

This application is based on and claims the benefit of priority from Taiwan Patent Application 102149353, filed on Dec. 31, 2013.

BACKGROUND

The present disclosure relates to a baseboard management controller (“BMC”) and a method of loading firmware by the BMC, and more particularly, to a BMC and a method of loading firmware by the BMC when a computer host has not yet been booted up.

Firmware in a BMC or in an operating system firmware interface can become corrupt due to the problems that occur during the writing process of firmware. In addition, firmware may need to be updated from time to time, particularly when the computer system is at the development and testing stages. The original firmware may fail once other hardware components are changed or modified.

SUMMARY

According to various embodiments of the present disclosure, a BMC is provided, which may include a bootloader and an interface to a removable storage device. The removable storage device may have a pre-stored first firmware file and a kernel. The bootloader may be configured to load the kernel from the removable storage device and run the kernel. The kernel may be configured to copy the first firmware file from the removable storage device.

When a computer system is at the development and testing stages, if firmware in the BMC or operating system firmware interface on a motherboard are corrupt, a solution is to return the entire motherboard to the manufacturer for replacement. Also, firmware updates can occur by accessing firmware files from storage devices through a south bridge chip, which is not feasible if the computer system is still at the development and testing stages, or when the computer system simply cannot be booted up at all. Further, updating firmware via trivial file transfer protocol (TFTP) requires the knowledge of additional and complicated network settings. A general computer system developer may not have knowledge of these settings and may need other specialists for help, which may add up cost and waste time.

By contrast, an embodiment of the present disclosure may allow a computer system developer to conduct firmware updates with a removable storage device, such as a portable and cheap USB disk dongle. A complete and non-damaged version (or a latest version) of firmware files may be stored in the removable storage device. When original firmware in the BMC or the operating system firmware interface on the motherboard are corrupt or need updates, one can just connect the removable storage device to the BMC through an appropriate interface, and the BMC can directly load and run a kernel from the removable storage device. Then the kernel may automatically copy firmware files as needed to replace the original firmware files in the BMC or in the operating system firmware interface.

The process discussed above may work if the BMC is powered. Further, by saving the intervention by the south bridge chip, the process can also work when the computer system has not been booted yet (or cannot be booted up). In addition, the process just described requires neither network support nor additional settings. Moreover, when the removable storage device is used with a motherboard, the removable storage device can be removed and applied to another motherboard, as opposed to disposing backup mechanisms on each motherboard. This can reduce the manufacturing cost compared with other approaches.

In an embodiment, the BMC may include a bootloader and an interface to a removable storage device. The removable storage device may have a pre-stored first firmware file and a kernel. And the bootloader may be configured to load the kernel from the removable storage device. The kernel may be configured to copy the first firmware file from the removable storage device to a first non-volatile memory.

In another embodiment, disclosed is a computer system including the BMC discussed above.

In yet another embodiment, disclosed is a method of firmware loading, applied to the BMC mentioned above, which includes connecting a removable storage device to an interface, wherein the removable storage device has a first firmware file, a second firmware file, and a kernel pre-stored thereon. A bootloader may load the kernel from the removable storage device. Moreover, the method may include copying another firmware file from the removable storage device to an operating system firmware interface, which is connected to the BMC.

Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages of the present disclosure should be or are in any single embodiment. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment. Thus, discussion of the features and advantages and similar language throughout this specification may, but do not necessarily, refer to the same embodiment.

Furthermore, the described features, advantages, and characteristic may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that any embodiments may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages will be readily understood, a more particular description briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only different embodiments, and are not therefore to be considered to be limiting of its scope, the present disclosure will be described and explained with additional specificity and detail through the use of the accompanying drawings.

FIG. 1 is a block diagram of a computer system according to an embodiment of the present disclosure.

FIG. 2 is a block diagram of a motherboard according to an embodiment of the present disclosure.

FIG. 3 is a flow chart of a method according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

As will be appreciated by one skilled in the art, the present disclosure may be embodied as a computer system, a method, or a computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, the present disclosure may take the form of a computer program product embodied in any tangible medium of expression having computer-usable program code embodied in the medium.

Any combination of one or more computer usable or computer readable medium(s) may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device. Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave. The computer usable program code may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer or server may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

The present disclosure is described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to various embodiments. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, may implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture, including instructions, which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

Referring now to FIG. 1 through FIG. 3, computer systems, methods, and computer program products are illustrated as structural or functional block diagrams or process flowcharts according to various embodiments of the present disclosure. The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

FIG. 1 illustrates the hardware framework of a computer system 10 according to an embodiment of the present disclosure. The computer system 10 includes a motherboard 15, and disposed on the motherboard 15, a BMC 100, and an operating system firmware interface 150. In an example, the computer system 10 is IBM's System x 3650 M4. In another example, the BMC 100 may be IBM's IMM (Integrate Management Module). In yet another example, the operating system firmware interface 150 could be implemented as a UEFI (Universal Extensible Firmware Interface), an EFI (Extensible Firmware Interface), or a BIOS (Basic Input/Output System), but the present disclosure is not limited thereto.

The BMC 100 may be communicatively connected to the operating system firmware interface 150, and is able to write data into the operating system firmware interface 150.

As shown in FIG. 1, a connector 110 on the motherboard 15 is provided for connecting a removable storage device 20 to the BMC 100. Structures of the connector 110 match the communication protocols between the removable storage device 20 to the BMC 100, and the present disclosure is not limited thereto. For more details please refer to FIG. 2 and the descriptions that follows.

FIG. 2 illustrates an embodiment of the BMC 100 and the operating system firmware interface 150 disposed on the motherboard 15. Note that this embodiment could be applied to the computer system 10, which is at the development and testing stages. In other words, the embodiment could be implemented with only the motherboard 15 shown in FIG. 2. A complete computer system as illustrated in FIG. 1 is not always necessary for the present disclosure.

First, the BMC 100 could have a non-volatile memory 102, which stores a firmware file 114. The operating system firmware interface 150 could have a non-volatile memory 152, which stores a second firmware file 154.

As shown in FIG. 2, the connector 110 of the motherboard 15 may connect the BMC 100 via an I/O port, port 108, of the BMC 100. The port 108 could be implemented as a GPIO which is adopted in a general BMC. Alternatively, the port 108 could be implemented as a specific port exclusively provided for communication with the removable storage device 20. The removable storage device 20 may store, in advance, the firmware file 30 for the BMC 100 and the firmware file 40 for the operating system firmware interface 150.

In an embodiment, the removable storage device 20 communicates with the BMC 100 through a USB protocol. Particularly, the removable storage device 20 may operate as a USB client and the BMC 100 may be a USB host. For this purpose, the BMC 100 may have a USB host controller 120 connected to the port 108, and the BMC 100 may operate as a USB host to detect and access the removable storage device 20 as a USB client.

In an embodiment, the BMC 100 may include a bootloader 104 and another I/O port, port 112, to receive an assertion signal SA sent by a user using a switch or a jumper (both not shown) on the motherboard 15. Once the assertion signal SA is received by the BMC 100, the bootloader 104 may load the firmware file 30 from the removable storage device 20, and run a kernel (such as a Linux kernel) according to the firmware file 30.

In an embodiment, the BMC 100 may include another I/O port, port 106, to send a light control signal SL to the light indicator 180 on the motherboard 15.

The process flow of the method according to an embodiment of the present disclosure is illustrated with FIG. 3 and described below with the components illustrated in FIGS. 1 and 2.

Step 300: a user connects the removable storage device 20 to the BMC 100 through the connector 110. A USB host controller 120 of the BMC 100 may detect the removable storage device 20 and establish data communications between the BMC 100 and the removable storage device 20 according to the USB protocol.

Step 302: the user may use a switch or a jumper (both not shown) on the motherboard 15 to send an assertion signal SA to the BMC 100. In response to the assertion signal SA, the BMC 100 may first check whether the firmware file 30 and the firmware file 40 stored in the removable storage device 20 are valid. If they are valid, then the process may go to step 304 as described below. If invalid, then the process may turn to step 314, where the BMC 100 proceeds according to predetermined policies, such as sending a light control signal SL to a light indicator 180 on the motherboard 150 as a warning.

Step 304: the bootloader 104 may load the firmware file 30 for the BMC 100 from the removable storage device 20, and run a kernel according to the firmware file 30 and proceed with the following steps 306 and 308. In an embodiment, the steps 306 and 308 could be executed in parallel. In another embodiment, the step 308 could precede the step 306.

Step 306: once the BMC 100 runs the kernel, the kernel can identify the firmware file 30 in the removable storage device 20 according to headers or other file information of the firmware file 30. Then the kernel may be run to copy the firmware file 30 from the removable storage device 20 to a non-volatile memory 102 of the BMC 100, to replace the original firmware file 114 stored in the non-volatile memory 102.

Step 308: once the BMC 100 runs the kernel, the kernel can identify the firmware file 40 in the removable storage device 20 according to a header or other file information of the firmware file 40. Particularly, the kernel can further verify the firmware file 40 in the removable storage device 20. Once verified, the firmware file 40 may be copied by the BMC 100 to a non-volatile memory 152 of the operating system firmware interface 150, to replace the original firmware file 154 stored in the non-volatile memory 152.

In addition to step 314, where the BMC 100 may send a light control signal SL to the light indicator 180 of the motherboard 15, the BMC 100 in steps 304, 306, and 308, can also send different light control signals SL to the light indicator 180 to have different colors of light or to flash at different frequencies. This shows the current status to the user, which may be desirable if the computer system 10, still at the development or testing states, is unable to be booted up at this moment and if the computer system 10 is not provided with a display device (not shown), or it fails to drive the display device.

The foregoing embodiments are provided to illustrate and disclose the technical features of the present disclosure, and are not intended to be restrictive of scope. Hence, all equivalent variations or modifications made to the foregoing embodiments without departing from the spirit embodied in the present disclosure should fall within the scope of the present disclosure as set forth in the appended claims. 

What is claimed is:
 1. A method of firmware loading, comprising: connecting a removable storage device to an interface, wherein the removable storage device has a first firmware file, a second firmware file, and a pre-stored kernel; and loading, by a bootloader, the kernel from the removable storage device.
 2. The method of claim 1, further comprising: running the kernel, by the bootloader, wherein the kernel when run by the bootloader, copies the first firmware file from the removable storage device to a first non-volatile memory.
 3. The method of claim 1, further comprising: running the kernel, by the bootloader, wherein the kernel when run by the bootloader copies the second firmware file from the removable storage device to an operating system firmware interface via the data interface. 